Curse

Necrus (Kliffington) · Dec 15, 2009, 05:59 PM // 17:59

My friend recently started Prophocies missions with his Dervish character, starting the Northern Wall mission he encountered a blue screen error never before seen until we started Proph -- and it happened as soon as the mission start counter reached zero... but according to the error code he is missing a .dll file called "ialmdev5.DLL"

Though we have found this .dll and placed it in several different folders in the Windows file, it did not correct the issue, and we are unsure if it's hardware or software related

It also happens if he takes a screenshot using the PrintScreen key
Normally it doesn't occur in normal gameplay, but starting the final mission in Nightfall it automatically blue screens when the counter ends

Any ideas? thoughts? ...solutions?

gone · Dec 15, 2009, 06:06 PM // 18:06

OS?
system specs?
have you updated drivers?

Necrus (Kliffington) · Dec 15, 2009, 06:18 PM // 18:18

He is using Windows XP
3 Ghz processing speed, 2 GB RAM
I believe he is using ATI Radeon video cards, two of them at 256mb or something close

We are updating his drivers now, but sorry I couldn't give you more informative specs, I'm not at his machine right now

Bob Slydell · Dec 15, 2009, 10:32 PM // 22:32

Try the drivers first and see if it helps. It's likely that card requires the driver along with that .dll in the driver folder.

That is quite an error, I'm stumped to why GW is looking for a .dll when everything it needs is in the .DAT. Unless the .DAT needs reimaging.

Quaker · Dec 16, 2009, 07:05 PM // 19:05

It's probably the OS that's looking for the dll, not GW.

You could try doing a "repair" of windows.

Short explanation: Boot from the windows CD and follow the procedure to install windows. When the installation gets to the point where it finds a "current windows installation" (usually C:\Windows), choose the "Repair this installation" option (press "R")
It will go through what looks like a normal install, but when it's finished everything will be just as it was except (hopefully) it will now work properly.
Note: at no point should you choose any option to format the drive (if you do come to a choice, tell it to leave the system as it is) and don't go for the "Repair using recovery console" option earlier in the process - that's not what you want.